Using and processing per slice segment identifiers in a network employing segment routing

ABSTRACT

The same prefix segment identifier (SID) may be configured and/or used for either (A) more than one prefix within an interior gateway protocol (IGP) domain, or (B) one prefix with more than one path computation algorithm within the IGP domain by: (a) receiving, by a node in the IGP domain, an IGP advertisement including both (1) a prefix SID and a segment routing global block (SRGB) slice identifier; (b) determining whether or not the SRGB slice identified by the SRGB slice identifier is provisioned on the node; and (c) responsive to a determination that the SRGB slice identified by the SRGB slice identifier is not provisioned on the node, not processing the prefix SID included in the received IGP advertisement, and otherwise responsive to a determination that the SRGB slice identified by the SRGB slice identifier is provisioned on the node, (1) processing the prefix SID and SRGB slice to generate a unique, per SRGB slice, MPLS label for the prefix, and (2) updating a label forwarding information base (LFIB) for the node using the unique, per SRGB slice, label for the prefix and the prefix.

§ 0. RELATED APPLICATION(S)

This application claims the benefit of U.S. Provisional Application No. 62/877,847 (referred to as “the '847 provisional” and incorporated herein by reference), titled “USING AND PROCESSING PER SLICE SEGMENT IDENTIFIERS IN A NETWORK EMPLOYING SEGMENT ROUTING,” filed on Jul. 24, 2019 and listing Raveendra Torvi, Abhishek Deshmukh, Tarek Saad and Vishnu Pavan Beeram as the inventors. The scope of the invention is not limited to any requirements of the specific embodiments in the '847 provisional.

§ 1. BACKGROUND OF THE INVENTION

§ 1.1 Field of the Invention

The present description concerns communications networks. More specifically, the present description concerns configuring and using prefix segment identifiers (SIDs) and/or segment routing global blocks (SRGBs) in a communications network segment employing segment routing (SR).

§ 1.2 Background Information

§ 1.2.1 Segment Routing

The Internet was initially designed to provide best-effort connectivity over a least-cost path. In today's Internet, however, many applications require more than best-effort connectivity over a least-cost path. Today, network operators are tasked with delivering advance services such as traffic engineering and fast reroute at scale. To deliver these advanced services at scale, network operators must reduce network complexity. Segment Routing (SR) offers an innovative approach to traffic steering. It can be applied to long-standing problems such as traffic engineering and fast reroute. When applied to these problems, SR can simplify routing protocols, network design and network operations.

Segment routing (also referred to as Source Packet Routing in Networking (“SPRING”)) is a control-plane architecture that enables an ingress router to steer a packet through a specific set of nodes and links in the network without relying on the intermediate nodes in the network to determine the actual path it should take. In this context, the term “source” means the point at which the explicit route is imposed. Segment routing is defined in “Segment Routing Architecture,” Request for Comments 8402 (July 2018, the Internet Engineering Task Force) (referred to as “RFC 8402” and incorporated herein by reference). SPRING enables automation of a network by using a software-defined network (“SDN”) controller for traffic steering and traffic engineering in a wide area network (“WAN”) packet network.

Segment routing leverages the source routing paradigm. A node steers a packet through an ordered list of instructions, called “segments.” For example, an ingress router (also referred to as “a headend router”) can steer a packet through a desired set of nodes and links by prepending the packet with segments that contain an appropriate combination of tunnels.

§ 1.2.1.1 SR Domain

An SR domain is a collection of nodes that participate in SR protocols. Within an SR domain, a node can execute ingress, transit, or egress procedures. FIG. 1 depicts a network in which a source node sends a packet to a destination node. The source and destination nodes reside outside of the SR domain, but the path between them traverses the SR domain. More specifically, when the packet arrives at the SR ingress node (R1), the ingress node subjects the packet to policy. Policy can associate a packet with an SR path. Policy includes match conditions and actions. If the packet satisfies match conditions, the SR ingress node (R1) can encapsulate the packet in an SR tunnel. The SR tunnel traverses an SR path to the egress node (R6).

The SR path can be engineered to satisfy any number of constraints (e.g., minimum link bandwidth, maximum path latency). While an SR path can follow the least cost path to the egress node, constraints can cause it to follow another path.

The source node and the SR ingress node may reside on independent hardware platforms (e.g., on a laptop and a router, respectively), or the source node and SR ingress node can reside on the same hardware (e.g., on a virtual machine and a hypervisor, respectively). Similarly, the SR egress node and the destination node can reside on independent hardware platforms, or on a single platform. In a less typical configuration, the source node resides within the SR domain. In this case, the source node is also the SR ingress node, because it executes SR ingress procedures Similarly, the destination node can reside within the SR domain, in which case, the destination node is also the SR egress node, because it executes SR egress procedures.

§ 1.2.1.2 SR Path

An SR path is an ordered list of segments that connects an SR ingress node to an SR egress node. Although an SR path can follow the least cost path from ingress to egress, it can also follow another path.

Different SR paths can share the same segment. For example, referring to FIG. 2, Path A connects ingress node A to egress node Z, while Path B connects ingress node B to the same egress node Z. Both paths A and B traverse Segment 3.

When an SR ingress node encapsulates a packet in an SR tunnel, it encodes the associated segment list in the tunnel header. It then forwards the packet downstream. Transit nodes process the tunnel header, forwarding the packet from the current segment to the next segment. Since the SR ingress node encodes path information in the tunnel header, transit nodes do not need to maintain information regarding each path that they support. Rather, the transit nodes are only required to process the tunnel header, forwarding the packet from the current segment to the next segment. This is a major benefit of SR. More specifically, since transit nodes are not required to maintain path information, overhead associated with maintaining that information is eliminated, routing protocols are simplified, scaling characteristics are improved, and network operations become less problematic.

§ 1.2.1.3 SR Segments and Segment Types

An SR segment is an instruction that causes a packet to traverse a section of the network topology. While a segment (i.e., an instruction) causes a packet to traverse a section of the network topology, it is distinct from that section of the network topology. SR defines many different SR segment types. Among these are the “adjacency segments” and “prefix segments.” Each of these types of segments is described below.

§ 1.2.1.3.1 Adjacency Segments

An adjacency segment is an instruction that causes a packet to traverse a specified link (i.e., a link that is associated with an IGP adjacency). FIG. 3 depicts an SR path that connects ingress node R1 to egress node R6. The path contains the following adjacency segments: (1) segment 1, instantiated on R1, causes packets to traverse link R1→R2; (2) segment 2, instantiated on R2, causes packets to traverse link R2→R3; and segment 3, instantiated on R3, causes packets to traverse link R3→R6. If any of the above-mentioned links becomes unavailable, so does the associated adjacency segment. Consequently, if any of the above-mentioned adjacency segments becomes unavailable, so does the entire path.

Thus, an adjacency segment is a strict forwarded single-hop tunnel that carries packets over a specific link between two nodes, irrespective of the link cost.

§ 1.2.1.3.2 Prefix Segments

A prefix segment is an instruction that causes a packet to traverse the least cost path (or a path determined using an identified algorithm) to a node or prefix. Referring to FIG. 4A, assume that all links are configured with the same interior gateway protocol (IGP) metric and that the SR path is to be a least cost (and therefore) shortest path. An SR path connects ingress node R1 to egress node R6 and contains the following prefix segments: (1) segment 1, instantiated on R1, causes packets to traverse the least cost path from R1 to R2; (2) segment 2, instantiated on R2 and R3, causes packets to traverse the least cost path from the instantiating node to R6. Consequently, when the links are all available, the SR path guides packets through the above-mentioned links and segments.

Referring to FIG. 4B, assume that the link R1→R2 becomes unavailable. When this occurs, the network establishes a new least cost path between R1 and R2. This new least cost path includes Links R1→R4, and R4→R2. Since the network has established a new least cost path between R1 and R2, segment 1 remains available and causes packets to traverse the new least cost path. The behavior of segment 2 is unchanged. Therefore, the path now traverses Links R1→R4, R4→R2, R2→R3 and R3→R6.

Thus, a prefix segment is a multihop tunnel that uses equal cost multi-hop aware shortest path links to reach a prefix. A prefix segment identifier (SID) supports both IPv4 and IPv6 prefixes. A node segment is a special case of prefix segment that uses shortest path links between two specific nodes.

§ 1.2.1.3.3 Anycast Segments

An IGP anycast segment is an IGP prefix segment that identifies a set of routers. An anycast segment enforces forwarding based on the equal-cost multipath-aware (ECMP-aware) shortest-path toward the closest node of the anycast set. Within an anycast group, all the routers advertise the same prefix with the same segment identifier (SID) value, which facilitates load balancing. Thus, an anycast segment is also a type of prefix segment that identifies a set of routers to advertise the same prefix with the same SID value.

§ 1.2.1.4 SR Multi-Protocol Label Switching (MPLS)

In SR-MPLS, SR paths are encoded as MPLS label stacks, with each label stack entry representing a segment in the SR path. The following describes how MPLS labels are used to encode adjacency and prefix segments.

§ 1.2.1.4.1 Using MPLS Labels to Encode Adjacency Segments

Referring to FIG. 5, an SR path connects R1 to R4. The SR path contains three adjacency segments. Segment 1 causes packets to traverse link R1→R2, segment 2 causes packets to traverse link R2→R3, and segment 3 causes packets to traverse link R3→R4. When R1 receives a packet from outside of the SR domain, it subjects the packet to policy. Policy may cause R1 to forward the packet through the SR path shown in FIG. 5. When this occurs, R1 imposes an MPLS label stack containing two entries. The entry at the top of the stack represents segment 2 and carries MPLS label 1002. The entry at the bottom of the stack represents segment 3 and carries MPLS label 1003.

Having imposed an MPLS label stack, R1 forwards the encapsulated packet through segment 1 (i.e., Link R1→R2). When the packet arrives at R2, R2 extracts the top label (i.e., 1002) from the label stack and searches for a corresponding entry in its Forwarding Information Base (“FIB”). The corresponding FIB entry includes an instruction (i.e., POP) and a next-hop (i.e., R3). Therefore, R2 pops the topmost label from the label stack and forwards the packet through segment 2 (i.e., Link R2→R3).

When the packet arrives at R3, R3 extracts the label (i.e., 1003) from the remaining label stack and searches for a corresponding entry in its FIB. The corresponding FIB entry includes an instruction (i.e., POP) and a next-hop (i.e., R4). Therefore, R3 pops the remaining entry from the label stack and forwards the packet through segment 3 (i.e., Link R3→R4). As shown in FIG. 5, after traversing the SR path, the packet arrives at R4 without MPLS encapsulation.

§ 1.2.1.4.2 Using MPLS Labels to Encode Prefix Segments

In FIG. 6, an SR path connects R1 to R7 via R4. The SR path contains two prefix segments. Segment 1 is a prefix segment that causes packets to traverse the (e.g., least cost) path from R1 to R4. Segment 2 is a prefix segment that causes packets to traverse the (e.g., least cost) path from R4 to R7. In this network, assume that all links are configured with the same IGP metric (e.g., 10). Therefore, the least cost path for the first segment from R1 to R4 traverses links R1→R2, R2→R3 and R3→R4, while the least cost path for the second segment from R4 to R7 traverses links R4→R8 and R8→R7.

When R1 receives a packet from outside of the SR domain, it subjects the packet to policy. Policy may cause R1 to forward the packet through the SR path shown in FIG. 6. When this occurs, R1 imposes an MPLS label stack containing two entries. The top entry of the label stack represents segment 1 and carries the label 2001. The bottom entry of the label stack represents segment 2 and carries the label 2002. Having imposed an MPLS label stack, R1 forwards the encapsulated packet into segment 1 via link R1→R2.

When the packet arrives at R2, R2 extracts the top label (i.e., 2001) from the label stack and searches for a corresponding entry in its FIB. The corresponding FIB entry includes an instruction (i.e., SWAP—3001) and a next-hop (i.e., R3). Therefore, R2 overwrites the topmost label with a new value (i.e., 3001) and forwards the packet to R3.

When the packet arrives at R3, R3 extracts the top label (i.e., 3001) from the label stack and searches for a corresponding entry in its FIB. The corresponding FIB entry includes an instruction (i.e., POP) and a next-hop (i.e., R4). Therefore, R3 pops the topmost entry from the label stack and forwards the packet into segment 2 via link R3→R4.

When the packet arrives at R4, R4 extracts the remaining label (i.e., 2002) from the label stack and searches for a corresponding entry in its FIB. The corresponding FIB entry includes an instruction (i.e., SWAP—3002) and a next-hop (i.e., R8). Therefore, R4 overwrites the remaining label with a new value (i.e., 3002) and forwards the packet to R8.

When the packet arrives at R8, R8 extracts the remaining label (i.e., 3002) from the label stack and searches for a corresponding entry in its FIB. The corresponding FIB entry includes an instruction (i.e., POP) and a next-hop (i.e., R7). Therefore, R8 pops the remaining entry from the label stack and forwards the packet to R7 without MPLS encapsulation.

§ 1.2.1.4.3 Penultimate Hop Popping (PHP) and the Explicit Null Label

In the examples above, each segment executes PHP procedures. That is, when a packet traverses a segment, the segment's penultimate node pops the label associated with the segment. If the SR path contains another segment, yet to be traversed, the current segment's egress node is also the ingress node of the next segment. In this case, the packet arrives at that node with the next segment's label exposed on the top of the stack. If the SR path does not contain another segment, yet to be traversed, the segment egress node is also the path egress node. In that case, the packet arrives at the path egress node without MPLS encapsulation.

In some cases, the final link in the SR path may not be able to carry the packet without MPLS encapsulation. For example, the packet may be IPv6, while the link supports IPv4 only. In order to prevent this problem, the SR ingress node can add an MPLS Explicit Null label to the top of the MPLS label stack.

When the penultimate node in the final segment pops the label associated with the final segment, it exposes the Explicit Null label. It then forwards the packet to the path egress node. The path egress node pops the Explicit Null label and continues to process the packet.

§ 1.2.1.5 Configuration and Distribution of Segment Identifiers (SIDs)

The foregoing examples described with respect to FIGS. 5 and 6 assumed that MPLS labels were distributed and each node's FIB was populated. Essentially segment routing engages interior gateway protocols (“IGPs”) like Intermediate-System Intermediate-System (“IS-IS”) and open shortest path first (“OSPF”) for advertising two types of network segments or tunnels—(1) a strict forwarded single-hop tunnel that carries packets over a specific link between two nodes, irrespective of the link cost (referred to as “adjacency segments,” which were described in § 1.2.1.3.1 above), and (2) a multihop tunnel using shortest path links between two specific nodes (referred to as “node segments,” which were described in § 1.2.1.3.2 above).

Each segment is associated with an identifier, which is referred to as the segment identifier (“SID”). As already noted above, an ordered list of segments is encoded as a stack of labels. A segment can represent any instruction, topological or service-based. A segment can have a local semantic to a segment routing node or to a global node within a segment routing domain. Segment routing enforces a flow through any topological path and service chain while maintaining per-flow state only at the ingress node to the segment routing domain. Segment routing can be directly applied to the MPLS architecture with no change on the forwarding plane. A segment is encoded as an MPLS label. An ordered list of segments is encoded as a “stack” of labels or “label stack.” The segment to be processed is on the top of the stack (i.e., the outermost label of the label stack). Upon completion of a segment, the related label is “popped” (i.e., removed) from the stack.

Segment routing can be applied to the IPv6 architecture, with a new type of routing extension header. A segment is encoded as an IPv6 address. An ordered list of segments is encoded as an ordered list of IPv6 addresses in the routing extension header. The segment to process is indicated by a pointer in the routing extension header. Upon completion of a segment, the pointer is incremented.

§ 1.2.1.5.1 Configurable Segment Routing Global Block

As already noted above, segment is encoded as an MPLS label. An ordered list of segments is encoded as a stack of labels. Every node in the segment routing domain is allocated labels by the node label manager based on the index range configured for source packet routing. These labels are allocated to the node segment based on the availability of the dynamic label range managed by node label manager. A segment routing global block (“SRGB”) is the range of label values used in segment routing. An available SRGB label range can be configured for the IS-IS and OSPF protocols so that the labels are predictable across segment routing domains. Thus, every node in the segment routing domain is allocated labels based on the availability of the dynamic label range, and the SRGB is the range of label values reserved for segment routing. A SID may be provided as an index to be added to an SRGB base value to obtain a label value.

The IS-IS protocol creates adjacency segments per adjacency, level, and address family (one each for IPv4 and IPv6). An MPLS label is allocated for each adjacency segment that gets created. These labels are allocated after the adjacency status of the segment changes to the up state. The OSPF protocol creates adjacency segments per adjacency.

§ 1.2.2 Limitations of Existing Prefix SIDs

The SR prefix SID, as defined in “IS-IS Extensions for Segment Routing,” draft-ietf-isis-segment-routing-extensions-25 (Internet Engineering Task Force, May 19, 2019) (incorporated herein by reference), is unique per IGP domain. This means a prefix SID assigned to a unicast prefix cannot be re-assigned to another prefix within the same IGP domain. As noted above, in MPLS networks, a prefix SID can be used with the SRGB to generate a unique label allocated on each router that receives the prefix SID in an IGP advertisement. For example, when using intermediate system-intermediate system (“IS-IS”) as the IGP, the prefix SID sub-TLV is carried in a prefix reachability Network Layer Reachability Information (“NLRI”) field (e.g., in TLV-135) and is flooded within the IGP domain. Every router in the IGP domain—including those in remote IGP area(s)—will potentially receive the prefix reachability NLRI with the prefix SID sub-TLV and will potentially process the prefix SID. This results in the allocation and assignment of the unique local label (derived from the SRGB) and to the specific prefix indicated in the prefix NLRI and the programing of its forwarding with the resulting set of the next-hop(s). Consequently, every node in the IGP domain will have to perform the same in processing upon receiving the prefix SID sub-TLV advertisement.

However, it is sometimes desirable to restrict the scope of a prefix SID to a specific set of router(s) within an IGP domain (e.g., to a color or affinity). The prefix may be reachable from only a sub-set of router(s) in the IGP domain. Consequently, only this sub-set will need to process the prefix SID and program its corresponding path(s) in their forwarding. Unfortunately, however, every node in the IGP domain will have to perform the same in processing upon receiving the prefix SID sub-TLV advertisement—even those nodes that do not belong to the specific set. Consider, for example, a multi (e.g., dual) plane usage case in a provider network, in which a service provider partitions their network into multiple (e.g., two) distinct plane(s) (e.g., for security, for service redundancy, for separation of different levels or qualities of service, etc.) In such a case, router(s) in one plane are reachable within the same plane. but are not to be reachable from any other plane. In SR today, this can be realized by “coloring” the plane(s) link(s) with different affinities and leveraging the prefix SID sub-TLV “algorithm” field to assign a unique prefix SID for each plane and to compute path(s) that restrict next-hop(s) to that specific plane. For example, a service provider may assign two distinct prefix SID(s) (e.g., GREEN prefix SID=1, and RED prefix SID=2) to the same prefix so it can be reachable over the two distinct plane(s) (e.g., the plane GREEN and the plane RED). Both (RED and GREEN) prefix SIDS will be advertised within the IGP domain and, hence, be received and processed by all routers in the network, regardless of whether or not they belong to the plane to which the prefix SID corresponds.

As indicated earlier, the GREEN prefix SID (SID=1), though used by only routers in plane GREEN, cannot be reused for any other prefix in the domain. Further, it won't be possible to reassign the label corresponding to the GREEN prefix SID on all domain routers to any other prefix.

In view of the foregoing, it would be useful to avoid processing plane-specific prefix SIDS by routers in the IGP domain but a different plane. It would also be useful to be able to reuse the same prefix SID by routers in the same IGP but different planes.

§ 2. SUMMARY OF THE INVENTION

The challenge(s) of being able to reuse the same prefix SID by routers in the same IGP but different planes, and/or avoiding the processing of plane-specific prefix SIDS by routers in the IGP domain but a different plane, is met by providing a computer-implemented method for configuring and/or using the same prefix segment identifier (SID) for either (A) more than one prefix within an interior gateway protocol (IGP) domain, or (B) one prefix with more than one path computation algorithm within the IGP domain. In some example embodiments consistent with the present description, the computer-implemented method includes (a) receiving, by a node in the IGP domain, an IGP advertisement including both (1) a prefix SID and a segment routing global block (SRGB) slice identifier; (b) determining whether or not the SRGB slice identified by the SRGB slice identifier is provisioned on the node; and (c) responsive to a determination that the SRGB slice identified by the SRGB slice identifier is not provisioned on the node, not processing the prefix SID included in the received IGP advertisement, and otherwise responsive to a determination that the SRGB slice identified by the SRGB slice identifier is provisioned on the node, (1) processing the prefix SID and SRGB slice to generate a unique, per SRGB slice, MPLS label for the prefix, and (2) updating a label forwarding information base (LFIB) for the node using the unique, per SRGB slice, label for the prefix and the prefix.

In some example embodiments consistent with the present description, the act of processing the prefix SID and SRGB slice to generate a unique, per SRGB slice, label for the prefix includes adding the prefix SID, as an index value, to a base defined by the SRGB slice. In some other example embodiments consistent with the present description, the act of processing the prefix SID and SRGB slice to generate a unique, per SRGB slice, label for the prefix includes subtracting the prefix SID, as an index value, from a maximum value defined by the SRGB slice.

In some example embodiments consistent with the present description, the LFIB for the node includes an entry with the unique, per SRGB slice, label for the prefix and the prefix. In such example embodiments, the computer-implemented method further comprises: (d) receiving a packet including the prefix; (e) using the prefix to look up the unique, per SRGB slice, label in the LFIB; and (f) forwarding the packet using the unique, per SRGB slice, label.

In some example embodiments consistent with the present description, the router belongs to a specific slice of an SR domain within the IGP domain. In some other example embodiments consistent with the present description, the router belongs to at least two specific slices of an SR domain within the IGP.

In some example embodiments consistent with the present description, the IGP advertisement is a prefix SID sub-TLV carried in a Network Layer Reachability Information (NLRI) field and including both (1) a prefix SID and a segment routing global block (SRGB) slice identifier.

In some example embodiments consistent with the present description, the SRGB slice corresponds to a ring.

In some example embodiments consistent with the present description, the generated IGP advertisement is transmitted, via IGP flooding, to all routers belonging to the IGP domain, regardless of whether or not such routers belong to the slice of the SR domain identified by the SRGB slice identifier.

§ 3. BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an example network used to illustrate an SR domain.

FIG. 2 is an example network used to illustrate SR paths through an SR domain.

FIG. 3 is an example network used to illustrate adjacency segments in an SR domain.

FIGS. 4A and 4B are an example network used to illustrate prefix segments in an SR domain.

FIG. 5 is an example network used to illustrate the use of MPLS labels derived from adjacency segments.

FIG. 6 is an example network used to illustrate the use of MPLS labels derived from prefix segments.

FIG. 7 is an example message format for carrying a slice identifier in connection with a SID, such as a prefix SID.

FIG. 8 is an example message format of a per-slice SRGB sub-TLV.

FIG. 9 is a flow diagram of an example method for using and/or configuring one prefix SID for more than one prefix in different slices (or one prefix with more than one path computation algorithm in different slices) within an IGP domain.

FIG. 10 illustrates two data forwarding systems, which may be used as nodes in an SR domain, coupled via communications links.

FIG. 11 is a block diagram of a router which may be used a node in an SR domain.

FIG. 12 is an example architecture in which ASICS may be distributed in a packet forwarding component to divide the responsibility of packet forwarding.

FIGS. 13A and 13B is an example of operations of the example architecture of FIG. 12.

FIG. 14 is a flow diagram of an example method for providing packet forwarding in an example router.

FIG. 15 is a block diagram of an exemplary machine 1500 that may perform one or more of the processes described, and/or store information used and/or generated by such processes.

FIG. 16 is an example network illustrating operations of an example method consistent with that of FIG. 9.

§ 4. DETAILED DESCRIPTION

The present disclosure may involve novel methods, apparatus, message formats, and/or data structures for improving the allocation and use of prefix SIDs, and improving their advertisement, in an IGP domain. The following description is presented to enable one skilled in the art to make and use the described embodiments, and is provided in the context of particular applications and their requirements. Thus, the following description of example embodiments provides illustration and description, but is not intended to be exhaustive or to limit the present disclosure to the precise form disclosed. Various modifications to the disclosed embodiments will be apparent to those skilled in the art, and the general principles set forth below may be applied to other embodiments and applications. For example, although a series of acts may be described with reference to a flow diagram, the order of acts may differ in other implementations when the performance of one act is not dependent on the completion of another act. Further, non-dependent acts may be performed in parallel. No element, act or instruction used in the description should be construed as critical or essential to the present description unless explicitly described as such. Also, as used herein, the article “a” is intended to include one or more items. Where only one item is intended, the term “one” or similar language is used. Thus, the present disclosure is not intended to be limited to the embodiments shown and the inventors regard their invention as any patentable subject matter described.

By limiting the scope of a prefix SID, example embodiments consistent with the present description allow for potentially reusing the same prefix SID to another prefix (or even same prefix with a different Algorithm) but for a different slice. In conventional SR protocols, such as existing protocols compliant with RFC 8402, there is single SRGB that is allocated, advertised, and managed by each SR node in the IGP domain. This restricts a prefix SID to always resolve to the same label in that SRGB space. Example embodiments consistent with the present description slice the per node SRGB into multiple slices (e.g., one for each color, or affinity, or plane), each identified by a unique identifier. The present description introduces a new field in the prefix SID sub-TLV to carry the SRGB Slice ID in the IGP advertisement. A node receiving a prefix SID sub-TLV with a Slice ID will resolve the prefix SID to a label in the specific SRGB with that Slice D. If the SRGB Slice ID is not provisioned on a node, the node can stop processing the prefix SID sub-TLV with that slice D.

First, as shown in the example message format 700 of FIG. 7, a prefix SID sub-TLV is extended to include Slice ID 750. More specifically, a router that hosts a prefix can assign a SID to a prefix within that can be reached over a one Slice. As shown in FIG. 7, the per Slice prefix SID sub-TLV contains the Slice ID 750 in addition to the SID/Label 760.

Next, as shown in the example message format 800 of FIG. 8, each node provisions and advertises an SRGB for a specific Slice ID. The range field 850 carries the SRGB range/size. The label field 860 carries the SRGB start. More specifically, any router in the IGP domain that receives the per Slice prefix SID sub-TLV, will first check if it is part of the slice (e.g., by inspecting if per Slice SRGB is provisioned. If the router is not part of the slice, it can stop processing the per slice prefix SID sub-TLV. If the router is part of the slice, it allocates the corresponding MPLS label derived from the per Slice SRGB.

§ 4.1 Example Method

FIG. 9 is a flow diagram of an example method 900 for using and/or configuring one prefix SID for more than one prefix (or one prefix with more than one path computation algorithm) within an IGP domain. The example method 900 may be run by a node (e.g., each node) of in the IGP domain including the SR domain. As shown, the example method 900 receives, by the node in the IGP, an IGP advertisement including both (1) a prefix SID and a segment routing global block (SRGB) slice identifier. (Block 910) Next, the example method 900 determines whether or not the SRGB slice identified by the SRGB slice identifier is provisioned on the node. (Block 920) Responsive to a determination that the SRGB slice identified by the SRGB slice identifier is not provisioned on the node (Decision 930, NO), the example method 900 does not process the prefix SID included in the received IGP advertisement. (Block 940) Otherwise, responsive to a determination that the SRGB slice identified by the SRGB slice identifier is provisioned on the node (Decision 930, YES), the example method 900 processes the prefix SID and SRGB slice to generate a unique (per slice) label for the prefix (Block 950) and updates a label forwarding information base (LFIB) for the node using the unique (per slice) label for the prefix and the prefix (Block 960).

Referring back to block 950, in some example embodiments consistent with the present description, the act of processing the prefix SID and SRGB slice to generate a unique (per slice) label for the prefix includes adding the prefix SID, as an index value, to a base defined by the SRGB slice. Alternatively, in some other example embodiments consistent with the present description, the act of processing the prefix SID and SRGB slice to generate a unique (per slice) label for the prefix includes subtracting the prefix SID, as an index value, from a maximum value defined by the SRGB slice.

§ 4.2 Example Apparatus

FIG. 10 illustrates two data forwarding systems 1010 and 1020 coupled via communications links 1030. The links may be physical links or “wireless” links. The data forwarding systems 1010,1020 may be routers for example, and may be RR and an RR-client. If the data forwarding systems 1010,1020 are example routers, each may include a control component (e.g., a routing engine) 1014,1024 and a forwarding component 1012,1022. Each data forwarding system 1010,1020 includes one or more interfaces 1016,1026 that terminate one or more communications links 1030. The example method 900 may be implemented on the control component 1014,1024 and may update information used by the forwarding component 1012,1022.

As just discussed above, and referring to FIG. 11, some example routers 1100 include a control component (e.g., routing engine) 1110 and a packet forwarding component (e.g., a packet forwarding engine) 1190.

The control component 1110 may include an operating system (OS) kernel 1120, routing protocol process(es) 1130, label-based forwarding protocol process(es) 1140, interface process(es) 1150, user interface (e.g., command line interface) process(es) 1160, and chassis process(es) 1170, and may store routing table(s) 1139, label forwarding information 1145, and forwarding (e.g., route-based and/or label-based) table(s) 1180. As shown, the routing protocol process(es) 1130 may support routing protocols such as the routing information protocol (“RIP”) 1131, the intermediate system-to-intermediate system protocol (“IS-IS”) 1132, the open shortest path first protocol (“OSPF”) 1133, the enhanced interior gateway routing protocol (“EIGRP”) 1134 and the boarder gateway protocol (“BGP”) 1135, and the label-based forwarding protocol process(es) 1140 may support protocols such as BGP 1135, the label distribution protocol (“LDP”) 1136 and the resource reservation protocol (“RSVP”) 1137. One or more components (not shown) may permit a user 1165 to interact with the user interface process(es) 1160. Similarly, one or more components (not shown) may permit an outside device to interact with one or more of the router protocol process(es) 1130, the label-based forwarding protocol process(es) 1140, the interface process(es) 1150, and the chassis process(es) 1170, via SNMP 1185, and such processes may send information to an outside device via SNMP 1185. Example embodiments consistent with the present description may be implemented in the boarder gateway protocol (“BGP”) process 1135.

The packet forwarding component 1190 may include a microkernel 1192, interface process(es) 1193, distributed ASICs 1194, chassis process(es) 1195 and forwarding (e.g., route-based and/or label-based) table(s) 1196.

In the example router 1100 of FIG. 11, the control component 1110 handles tasks such as performing routing protocols, performing label-based forwarding protocols, control packet processing, etc., which frees the packet forwarding component 1190 to forward received packets quickly. That is, received control packets (e.g., routing protocol packets and/or label-based forwarding protocol packets) are not fully processed on the packet forwarding component 1190 itself, but are passed to the control component 1110, thereby reducing the amount of work that the packet forwarding component 1190 has to do and freeing it to process packets to be forwarded efficiently. Thus, the control component 1110 is primarily responsible for running routing protocols and/or label-based forwarding protocols, maintaining the routing tables and/or label forwarding information, sending forwarding table updates to the packet forwarding component 1190, and performing system management. The example control component 1110 may handle routing protocol packets, provide a management interface, provide configuration management, perform accounting, and provide alarms. The processes 1130, 1140, 1150, 1160 and 1170 may be modular, and may interact with the OS kernel 1120. That is, nearly all of the processes communicate directly with the OS kernel 1120. Using modular software that cleanly separates processes from each other isolates problems of a given process so that such problems do not impact other processes that may be running. Additionally, using modular software facilitates easier scaling.

Still referring to FIG. 11, the example OS kernel 1120 may incorporate an application programming interface (“API”) system for external program calls and scripting capabilities. The control component 1110 may be based on an Intel PCI platform running the OS from flash memory, with an alternate copy stored on the router's hard disk. The OS kernel 1120 is layered on the Intel PCI platform and establishes communication between the Intel PCI platform and processes of the control component 1110. The OS kernel 1120 also ensures that the forwarding tables 1196 in use by the packet forwarding component 1190 are in sync with those 1180 in the control component 1110. Thus, in addition to providing the underlying infrastructure to control component 1110 software processes, the OS kernel 1120 also provides a link between the control component 1110 and the packet forwarding component 1190.

Referring to the routing protocol process(es) 1130 of FIG. 11, this process(es) 1130 provides routing and routing control functions within the platform. In this example, the RIP 1131, ISIS 1132, OSPF 1133 and EIGRP 1134 (and BGP 1135) protocols are provided. Naturally, other routing protocols may be provided in addition, or alternatively. Similarly, the label-based forwarding protocol process(es) 1140 provides label forwarding and label control functions. In this example, the LDP 1136 and RSVP 1137 (and BGP 1135) protocols are provided. Naturally, other label-based forwarding protocols (e.g., MPLS, SR, etc.) may be provided in addition, or alternatively. In the example router 1100, the routing table(s) 1139 is produced by the routing protocol process(es) 1130, while the label forwarding information 1145 is produced by the label-based forwarding protocol process(es) 1140.

Still referring to FIG. 11, the interface process(es) 1150 performs configuration of the physical interfaces (Recall, e.g., 1016 and 1026 of FIG. 10.) and encapsulation.

The example control component 1110 may provide several ways to manage the router. For example, it 1110 may provide a user interface process(es) 1160 which allows a system operator 1165 to interact with the system through configuration, modifications, and monitoring. The SNMP 1185 allows SNMP-capable systems to communicate with the router platform. This also allows the platform to provide necessary SNMP information to external agents. For example, the SNMP 1185 may permit management of the system from a network management station running software, such as Hewlett-Packard's Network Node Manager (“HP-NNM”), through a framework, such as Hewlett-Packard's OpenView. Accounting of packets (generally referred to as traffic statistics) may be performed by the control component 1110, thereby avoiding slowing traffic forwarding by the packet forwarding component 1190.

Although not shown, the example router 1100 may provide for out-of-band management, RS-232 DB9 ports for serial console and remote management access, and tertiary storage using a removable PC card. Further, although not shown, a craft interface positioned on the front of the chassis provides an external view into the internal workings of the router. It can be used as a troubleshooting tool, a monitoring tool, or both. The craft interface may include LED indicators, alarm indicators, control component ports, and/or a display screen. Finally, the craft interface may provide interaction with a command line interface (“CLI”) 1160 via a console port, an auxiliary port, and/or a management Ethernet port

The packet forwarding component 1190 is responsible for properly outputting received packets as quickly as possible. If there is no entry in the forwarding table for a given destination or a given label and the packet forwarding component 1190 cannot perform forwarding by itself, it 1190 may send the packets bound for that unknown destination off to the control component 1110 for processing. The example packet forwarding component 1190 is designed to perform Layer 2 and Layer 3 switching, route lookups, and rapid packet forwarding.

As shown in FIG. 11, the example packet forwarding component 1190 has an embedded microkernel 1192, interface process(es) 1193, distributed ASICs 1194, and chassis process(es) 1195, and stores a forwarding (e.g., route-based and/or label-based) table(s) 1196. The microkernel 1192 interacts with the interface process(es) 1193 and the chassis process(es) 1195 to monitor and control these functions. The interface process(es) 1192 has direct communication with the OS kernel 1120 of the control component 1110. This communication includes forwarding exception packets and control packets to the control component 1110, receiving packets to be forwarded, receiving forwarding table updates, providing information about the health of the packet forwarding component 1190 to the control component 1110, and permitting configuration of the interfaces from the user interface (e.g., CLI) process(es) 1160 of the control component 1110. The stored forwarding table(s) 1196 is static until a new one is received from the control component 1110. The interface process(es) 1193 uses the forwarding table(s) 1196 to look up next-hop information. The interface process(es) 1193 also has direct communication with the distributed ASICs 1194. Finally, the chassis process(es) 1195 may communicate directly with the microkernel 1192 and with the distributed ASICs 1194.

In the example router 1100, the example method 900 may be implemented in the packet control component 1110.

Referring back to distributed ASICs 1194 of FIG. 11, FIG. 12 is an example of how the ASICS may be distributed in the packet forwarding component 1190 to divide the responsibility of packet forwarding. As shown in FIG. 12, the ASICs of the packet forwarding component 1190 may be distributed on physical interface cards (“PICs”) 1210, flexible PIC concentrators (“FPCs”) 1220, a midplane or backplane 1230, and a system control board(s) 1240 (for switching and/or forwarding). Switching fabric is also shown as a system switch board (“SSB”), or a switching and forwarding module (“SFM”) 1250. Each of the PICs 1210 includes one or more PIC I/O managers 1215. Each of the FPCs 1220 includes one or more I/O managers 1222, each with an associated memory 1224. The midplane/backplane 1230 includes buffer managers 1235 a, 1235 b. Finally, the system control board 1240 includes an internet processor 1242 and an instance of the forwarding table 1244 (Recall, e.g., 1196 of FIG. 11).

Still referring to FIG. 12, the PICs 1210 contain the interface ports. Each PIC 1210 may be plugged into an FPC 1220. Each individual PIC 1210 may contain an ASIC that handles media-specific functions, such as framing or encapsulation. Some example PICs 1210 provide SDH/SONET, ATM, Gigabit Ethernet, Fast Ethernet, and/or DS3/E3 interface ports.

An FPC 1220 can contain from one or more PICs 1210, and may carry the signals from the PICs 1210 to the midplane/backplane 1230 as shown in FIG. 12.

The midplane/backplane 1230 holds the line cards. The line cards may connect into the midplane/backplane 1230 when inserted into the example router's chassis from the front. The control component (e.g., routing engine) 1110 may plug into the rear of the midplane/backplane 1230 from the rear of the chassis. The midplane/backplane 1230 may carry electrical (or optical) signals and power to each line card and to the control component 1110.

The system control board 1240 may perform forwarding lookup. It 1240 may also communicate errors to the routing engine. Further, it 1240 may also monitor the condition of the router based on information it receives from sensors. If an abnormal condition is detected, the system control board 1240 may immediately notify the control component 1110.

Referring to FIGS. 12, 13A and 13B, in some exemplary routers, each of the PICs 1210,1110′ contains at least one I/O manager ASIC 1215 responsible for media-specific tasks, such as encapsulation. The packets pass through these I/O ASICs on their way into and out of the router. The I/O manager ASIC 1215 on the PIC 1210,1110′ is responsible for managing the connection to the I/O manager ASIC 1222 on the FPC 1220,1120′, managing link-layer framing and creating the bit stream, performing cyclical redundancy checks (CRCs), and detecting link-layer errors and generating alarms, when appropriate. The FPC 1220 includes another I/O manager ASIC 1222. This ASIC 1222 takes the packets from the PICs 1210 and breaks them into (e.g., 74-byte) memory blocks. This FPC I/O manager ASIC 1222 sends the blocks to a first distributed buffer manager (DBM) 1235 a′, decoding encapsulation and protocol-specific information, counting packets and bytes for each logical circuit, verifying packet integrity, and applying class of service (CoS) rules to packets. At this point, the packet is first written to memory. More specifically, the example DBM ASIC 1235 a′ manages and writes packets to the shared memory 1224 across all FPCs 1220. In parallel, the first DBM ASIC 1235 a′ also extracts information on the destination of the packet and passes this forwarding-related information to the Internet processor 1242/1142′. The Internet processor 1242/1142′ performs the route lookup using the forwarding table 1244 and sends the information over to a second DBM ASIC 1235 b′. The Internet processor ASIC 1242/1142′ also collects exception packets (i.e., those without a forwarding table entry) and sends them to the control component 1110. The second DBM ASIC 1235 b′ then takes this information and the 74-byte blocks and forwards them to the I/O manager ASIC 1222 of the egress FPC 1220/1120′ (or multiple egress FPCs, in the case of multicast) for reassembly. (Thus, the DBM ASICs 1235 a′ and 1235 b′ are responsible for managing the packet memory 1224 distributed across all FPCs 1220/1120′, extracting forwarding-related information from packets, and instructing the FPC where to forward packets.)

The I/O manager ASIC 1222 on the egress FPC 1220/1120′ may perform some value-added services. In addition to incrementing time to live (“TTL”) values and re-encapsulating the packet for handling by the PIC 1210, it can also apply class-of-service (CoS) rules. To do this, it may queue a pointer to the packet in one of the available queues, each having a share of link bandwidth, before applying the rules to the packet. Queuing can be based on various rules. Thus, the I/O manager ASIC 1222 on the egress FPC 1220/1120′ may be responsible for receiving the blocks from the second DBM ASIC 1235 b′, incrementing TTL values, queuing a pointer to the packet, if necessary, before applying CoS rules, re-encapsulating the blocks, and sending the encapsulated packets to the PIC I/O manager ASIC 1215.

FIG. 14 is a flow diagram of an example method 1400 for providing packet forwarding in the example router. The main acts of the method 1400 are triggered when a packet is received on an ingress (incoming) port or interface. (Event 1410) The types of checksum and frame checks that are required by the type of medium it serves are performed and the packet is output, as a serial bit stream. (Block 1420) The packet is then decapsulated and parsed into (e.g., 64-byte) blocks. (Block 1430) The packets are written to buffer memory and the forwarding information is passed on the Internet processor. (Block 1440) The passed forwarding information is then used to lookup a route in the forwarding table. (Block 1450) Note that the forwarding table can typically handle unicast packets that do not have options (e.g., accounting) set, and multicast packets for which it already has a cached entry. Thus, if it is determined that these conditions are met (YES branch of Decision 1460), the packet forwarding component finds the next hop and egress interface, and the packet is forwarded (or queued for forwarding) to the next hop via the egress interface (Block 1470) before the method 1400 is left (Node 1490) Otherwise, if these conditions are not met (NO branch of Decision 1460), the forwarding information is sent to the control component 1110 for advanced forwarding resolution (Block 1480) before the method 1400 is left (Node 1490).

Referring back to block 1470, the packet may be queued. Actually, as stated earlier with reference to FIG. 12, a pointer to the packet may be queued. The packet itself may remain in the shared memory. Thus, all queuing decisions and CoS rules may be applied in the absence of the actual packet. When the pointer for the packet reaches the front of the line, the I/O manager ASIC 1222 may send a request for the packet to the second DBM ASIC 1235 b. The DBM ASIC 1235 reads the blocks from shared memory and sends them to the I/O manager ASIC 1222 on the FPC 1220, which then serializes the bits and sends them to the media-specific ASIC of the egress interface. The I/O manager ASIC 1215 on the egress PIC 1210 may apply the physical-layer framing, perform the CRC, and send the bit stream out over the link.

Referring back to block 1480 of FIG. 14, as well as FIG. 12, regarding the transfer of control and exception packets, the system control board 1240 handles nearly all exception packets. For example, the system control board 1240 may pass exception packets to the control component 1110.

Although example embodiments consistent with the present invention may be implemented on the example routers of FIG. 10 or 11, embodiments consistent with the present invention may be implemented on communications network nodes (e.g., routers, switches, etc.) having different architectures. More generally, embodiments consistent with the present invention may be implemented on an example system 1400 as illustrated on FIG. 15.

FIG. 15 is a block diagram of an exemplary machine 1500 that may perform one or more of the processes described, and/or store information used and/or generated by such processes. The exemplary machine 1500 includes one or more processors 1510, one or more input/output interface units 1530, one or more storage devices 1520, and one or more system buses and/or networks 1540 for facilitating the communication of information among the coupled elements. One or more input devices 1532 and one or more output devices 1534 may be coupled with the one or more input/output interfaces 1530. The one or more processors 1510 may execute machine-executable instructions (e.g., C or C++ running on the Linux operating system widely available from a number of vendors such as Red Hat, Inc. of Durham, N.C.) to effect one or more aspects of the present invention. At least a portion of the machine executable instructions may be stored (temporarily or more permanently) on the one or more storage devices 1520 and/or may be received from an external source via one or more input interface units 1530. The machine executable instructions may be stored as various software modules, each module performing one or more operations. Functional software modules are examples of components of the invention.

In some embodiments consistent with the present invention, the processors 1510 may be one or more microprocessors and/or ASICs. The bus 1540 may include a system bus. The storage devices 1520 may include system memory, such as read only memory (ROM) and/or random access memory (RAM). The storage devices 1520 may also include a hard disk drive for reading from and writing to a hard disk, a magnetic disk drive for reading from or writing to a (e.g., removable) magnetic disk, an optical disk drive for reading from or writing to a removable (magneto-) optical disk such as a compact disk or other (magneto-) optical media, or solid-state non-volatile storage.

Some example embodiments consistent with the present invention may also be provided as a machine-readable medium for storing the machine-executable instructions. The machine-readable medium may be non-transitory and may include, but is not limited to, flash memory, optical disks, CD-ROMs, DVD ROMs, RAMs, EPROMs, EEPROMs, magnetic or optical cards or any other type of machine-readable media suitable for storing electronic instructions. For example, example embodiments consistent with the present invention may be downloaded as a computer program which may be transferred from a remote computer (e.g., a server) to a requesting computer (e.g., a client) by way of a communication link (e.g., a modem or network connection) and stored on a non-transitory storage medium. The machine-readable medium may also be referred to as a processor-readable medium.

Example embodiments consistent with the present invention (or components or modules thereof) might be implemented in hardware, such as one or more field programmable gate arrays (“FPGAs”), one or more integrated circuits such as ASICs, one or more network processors, etc. Alternatively, or in addition, embodiments consistent with the present invention (or components or modules thereof) might be implemented as stored program instructions executed by a processor. Such hardware and/or software might be provided in an addressed data (e.g., packet, cell, etc.) forwarding device (e.g., a switch, a router, etc.), a laptop computer, desktop computer, a tablet computer, a mobile phone, a software defined network (SDN) server, or any device that has computing and networking capabilities.

§ 4.3 Example of Operation of Example Method

FIG. 16 is an example network illustrating operations of an example method consistent with that of FIG. 9. In FIG. 16, the cross-hatched area 1610 corresponds to a red slice and the hatched area 1620 corresponds to a green slice. Although not shown, it is possible for a given node to belong to both slices. Further, in FIG. 16:

R6 has the following configs:

Prefix 6.6.6.61/32, prefix SID=1, Slice-ID=1 (RED)

Prefix 6.6.6.62/32, prefix SID=1, Slice-ID=2 (GREEN)

R2, R4 routers have the following configs:

SRGB for Slice-ID=1 (RED), start-label=16000

R1, R3 routers have the following configs:

SRGB for Slice-ID=2 (GREEN), start-label=16000

R5, R6 routers have the following configs:

SRGB for Slice-ID=1 (RED), start-label=18000

SRGB for Slice-ID=2 (GREEN), start-label=19000

R2 and R4 routers will both receive and only process the per Slice prefix SID=1 for Slice-ID=1 (RED). As a result, R2 and R4 allocate label 16001 (=16000+1) for prefix 6.6.6.61/32.

R1 and R3 routers will both receive and only process the per Slice prefix SID=1 for Slice-ID=2 (GREEN). R1 and R3 allocate label 16001(=16000+1) for prefix 6.6.6.62/32. Note that label SID=1 and label=16001 is reused on R2,R4 and R1,R3, in association with different prefixes.

R5 and R6 routers will both receive and only process the per Slice prefix SID=1 for Slice-ID=1 (RED) and per Slice prefix SID=1 for Slice-ID=2 (GREEN). R5 and R6 will allocate:

18001 (=18000+1) for prefix 6.6.6.61/32; and

19001 (=19000+1) for prefix 6.6.6.62/32

§ 4.4 Alternatives, Extensions and Refinements

This solution can be extended to Rings. (See, e.g., U.S. Provisional application Ser. No. 16/871,588, titled “RESILIENT MULTIPROTOCOL LABEL SWITCHING (MPLS) RINGS USING SEGMENT ROUTING”, filed on Jul. 8, 2019, and listing Raveendra Torvi, Abhishek Deshmukh, Kireeti Kompella, Tarek Saad, Vishnu Pavan Beeram and Ronald Bonica as inventors. A slice can be thought of as a Ring, and ring nodes can be thought of as routers that belong to the slice. The Ring-SID can be analogous with a Slice SID where the Slice-ID is the Ring-ID. This solution is applicable to networks that deploy segment-routing techniques for MPLS and IPv6 for SRv6 data plane technologies, among others.

§ 4.5 Conclusions

Example embodiments consistent with the present description allow the re-use of SR SIDS per slice within same IGP domain. They allow allocation of labels and programing of path(s) only on the routers belonging to the slice. This helps to scale the SID/label space to carry more IP prefixes, or more prefix-algorithm combinations. 

What is claimed is:
 1. A computer-implemented method for configuring and/or using the same prefix segment identifier (SID) provided for either (A) more than one prefix within an interior gateway protocol (IGP) domain, or (B) one prefix with more than one path computation algorithm within the IGP domain, the computer-implemented method comprising: a) receiving, by a node in the IGP domain, an IGP advertisement including both (1) a prefix SID and (2) a segment routing global block (SRGB) slice identifier; b) determining whether or not the SRGB slice identified by the SRGB slice identifier is provisioned on the node; and c) responsive to a determination that the SRGB slice identified by the SRGB slice identifier is not provisioned on the node, not processing the prefix SID included in the received IGP advertisement, and otherwise responsive to a determination that the SRGB slice identified by the SRGB slice identifier is provisioned on the node, 1) processing the prefix SID and SRGB slice to generate a unique, per SRGB slice, MPLS label for each of the one or more prefix for which the prefix SID is provided, and 2) updating a label forwarding information base (LFIB) for the node using the unique, per SRGB slice, MPLS label for each of the one or more prefix for which the prefix SID is provided and the one or more prefix for which the prefix SID is provided.
 2. The computer implemented method of claim 1 wherein the act of processing the prefix SID and SRGB slice to generate a unique, per SRGB slice, label for the prefix includes adding the prefix SID, as an index value, to a base defined by the SRGB slice.
 3. The computer implemented method of claim 1 wherein the act of processing the prefix SID and SRGB slice to generate a unique, per SRGB slice, label for the prefix includes subtracting the prefix SID, as an index value, from a maximum value defined by the SRGB slice.
 4. The computer-implemented method of claim 1 wherein the LFIB for the node includes an entry with the unique, per SRGB slice, label for the prefix and the prefix, the computer-implemented method further comprising: d) receiving a packet including the prefix; e) using the prefix to look up the unique, per SRGB slice, label in the LFIB; and f) forwarding the packet using the unique, per SRGB slice, label.
 5. The computer-implemented method of claim 1, wherein the router belongs to a specific slice of an SR domain within the IGP domain.
 6. The computer-implemented method of claim 1, wherein the router belongs to at least two specific slices of an SR domain within the IGP.
 7. The computer-implemented method of claim 1, wherein the same prefix SID is provided for more than one prefix within the IGP domain.
 8. The computer-implemented method of claim 1, wherein the same prefix SID is provided for one prefix with more than one path computation algorithm within the IGP domain.
 9. The computer-implemented method of claim 1, wherein the IGP advertisement is a prefix SID sub-TLV carried in a Network Layer Reachability Information (NLRI) field and including both (1) the prefix SID and the segment routing global block (SRGB) slice identifier.
 10. The computer-implemented method of claim 1, wherein the SRGB slice corresponds to a ring.
 11. A network device for configuring and/or using the same prefix segment identifier (SID) provided for either (A) more than one prefix within an interior gateway protocol (IGP) domain, or (B) one prefix with more than one path computation algorithm within the IGP domain, the device comprising: a) an interface; b) at least one processor; and c) a storage device storing processor-executable instructions which, when executed by the at least one processor, cause the at least one processor to perform a method responsive to receiving, by the interface, an IGP advertisement including both (1) a prefix SID and (2) a segment routing global block (SRGB) slice identifier, the method including 1) determining whether or not the SRGB slice identified by the SRGB slice identifier is provisioned on the network device, and 2) responsive to a determination that the SRGB slice identified by the SRGB slice identifier is not provisioned on the network device, not processing the prefix SID included in the received IGP advertisement, and otherwise responsive to a determination that the SRGB slice identified by the SRGB slice identifier is provisioned on the network device, processing the prefix SID and SRGB slice to generate a unique, per SRGB slice, MPLS label for each of the one or more prefix for which the prefix SID is provided, and updating a label forwarding information base (LFIB) for the node using the unique, per SRGB slice, MPLS label for each of the one or more prefix for which the prefix SID is provided and the one or more prefix for which the prefix SID is provided.
 12. A non-transitory computer-readable medium storing computer-executable instructions which, when executed by at least one computer, cause the computer to perform a computer-implemented method for configuring and/or using the same prefix segment identifier (SID) provided for either (A) more than one prefix within an interior gateway protocol (IGP) domain, or (B) one prefix with more than one path computation algorithm within the IGP domain, the computer-implemented method including a) receiving, by a node in the IGP domain, an IGP advertisement including both (1) a prefix SID and (2) a segment routing global block (SRGB) slice identifier, b) determining whether or not the SRGB slice identified by the SRGB slice identifier is provisioned on the node, and c) responsive to a determination that the SRGB slice identified by the SRGB slice identifier is not provisioned on the node, not processing the prefix SID included in the received IGP advertisement, and otherwise responsive to a determination that the SRGB slice identified by the SRGB slice identifier is provisioned on the node, 1) processing the prefix SID and SRGB slice to generate a unique, per SRGB slice, MPLS label for each of the one or more prefix for which the prefix SID is provided, 2) updating a label forwarding information base (LFIB) for the node using the unique, per SRGB slice, MPLS label for each of the one or more prefix for which the prefix SID is provided and the one or more prefix for which the prefix SID is provided. 